Mobile videoconferencing robot system with network adaptive driving

ABSTRACT

A remote control station that controls a robot through a network. The remote control station transmits a robot control command that includes information to move the robot. The remote control station monitors at least one network parameter and scales the robot control command as a function of the network parameter. For example, the remote control station can monitor network latency and scale the robot control command to slow down the robot with an increase in the latency of the network. Such an approach can reduce the amount of overshoot or overcorrection by a user driving the robot.

REFERENCE TO CROSS-RELATED APPLICATION

This application claims priority to Application No. 61/098,156 filed onSep. 18, 2008.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The subject matter disclosed generally relates to the field of mobiletwo-way teleconferencing.

2. Background Information

Robots have been used in a variety of applications ranging from remotecontrol of hazardous material to assisting in the performance ofsurgery. For example, U.S. Pat. No. 5,762,458 issued to Wang et al.discloses a system that allows a surgeon to perform minimally invasivemedical procedures through the use of robotically controlledinstruments. One of the robotic arms in the Wang system moves anendoscope that has a camera. The camera allows a surgeon to view asurgical area of a patient.

There has been marketed a mobile robot introduced by InTouchTechnologies, Inc., the assignee of this application, under thetrademarks COMPANION and RP-7. The InTouch robot is controlled by a userat a remote station. The remote station may be a personal computer witha joystick that allows the user to remotely control the movement of therobot. Both the robot and the remote station have cameras, monitors,speakers and microphones to allow for two-way video/audio communication.The robot camera provides video images to a screen at the remote stationso that the user can view the robot's surroundings and move the robotaccordingly.

The InTouch robot system typically utilizes a broadband network such asthe Internet to establish the communication channel between the remotestation and the robot. For various reasons the network may create anundesirable latency in the transmission of video from the robot to theremote station. When driving the robot the user primarily uses the videoprovided by the robot camera. Latency in the network may result in theuser receiving delayed video images and cause the user to generate robotcontrol commands that overshoot or overcorrect the movement of therobot.

BRIEF SUMMARY OF THE INVENTION

A remote control station that controls a robot through a network. Theremote control station transmits a robot control command that includesinformation to move the robot. The remote control station monitors atleast one network parameter and scales the robot control command as afunction of the network parameter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an illustration of a robotic system;

FIG. 2 is a schematic of an electrical system of a robot;

FIG. 3 is a further schematic of the electrical system of the robot;

FIG. 4 is a graphical user interface of a remote station;

FIG. 5 is an illustration showing a process for scaling a robot controlcommand;

FIG. 6 is a graph showing transfer functions for scaling the robotcontrol command based on a ping time; and,

FIG. 7 is a graph showing transfer functions for scaling the robotcontrol command based on a video rate.

DETAILED DESCRIPTION

Disclosed is a remote control station that controls a robot through anetwork. The remote control station transmits a robot control commandthat includes information to move the robot. The remote control stationmonitors at least one network parameter and scales the robot controlcommand as a function of the network parameter. For example, the remotecontrol station can monitor network latency and scale the robot controlcommand to slow down the robot with an increase in the latency of thenetwork. Such an approach can reduce the amount of overshoot orovercorrection by a user driving the robot.

Referring to the drawings more particularly by reference numbers, FIG. 1shows a robotic system 10 that can be used to conduct a remote visit.The robotic system 10 includes a robot 12, a base station 14 and aremote control station 16. The remote control station 16 may be coupledto the base station 14 through a network 18. By way of example, thenetwork 18 may be either a packet switched network such as the Internet,or a circuit switched network such has a Public Switched TelephoneNetwork (PSTN) or other broadband system. The base station 14 may becoupled to the network 18 by a modem 20 or other broadband networkinterface device. By way of example, the base station 14 may be awireless router. Alternatively, the robot 12 may have a directconnection to the network thru for example a satellite.

The remote control station 16 may include a computer 22 that has amonitor 24, a camera 26, a microphone 28 and a speaker 30. The computer22 may also contain an input device 32 such as a joystick or a mouse.The control station 16 is typically located in a place that is remotefrom the robot 12. Although only one remote control station 16 is shown,the system 10 may include a plurality of remote stations. In general anynumber of robots 12 may be controlled by any number of remote stations16 or other robots 12. For example, one remote station 16 may be coupledto a plurality of robots 12, or one robot 12 may be coupled to aplurality of remote stations 16, or a plurality of robots 12.

Each robot 12 includes a movement platform 34 that is attached to arobot housing 36. Also attached to the robot housing 36 is a pair ofcameras 38, a monitor 40, a microphone(s) 42 and a speaker(s) 44. Themicrophone 42 and speaker 30 may create a stereophonic sound. The robot12 may also have an antenna 46 that is wirelessly coupled to an antenna48 of the base station 14. The system 10 allows a user at the remotecontrol station 16 to move the robot 12 through operation of the inputdevice 32. The robot camera 38 is coupled to the remote monitor 24 sothat a user at the remote station 16 can view a patient. Likewise, therobot monitor 40 is coupled to the remote camera 26 so that the patientcan view the user. The microphones 28 and 42, and speakers 30 and 44,allow for audible communication between the patient and the user.

The remote station computer 22 may operate Microsoft OS software andWINDOWS XP or other operating systems such as LINUX. The remote computer22 may also operate a video driver, a camera driver, an audio driver anda joystick driver. The video images may be transmitted and received withcompression software such as MPEG CODEC.

FIGS. 2 and 3 show an embodiment of a robot 12. Each robot 12 mayinclude a high level control system 50 and a low level control system52. The high level control system 50 may include a processor 54 that isconnected to a bus 56. The bus 56 is coupled to the camera 38 by aninput/output (I/O) ports 58. The monitor 40 is coupled to the bus 56 bya serial output port 60 and a VGA driver 62. The monitor 40 may includea touchscreen function that allows the patient to enter input bytouching the monitor screen.

The speaker 44 is coupled to the bus 56 by a digital to analog converter64. The microphone 42 is coupled to the bus 56 by an analog to digitalconverter 66. The high level controller 50 may also contain randomaccess memory (RAM) device 68, a non-volatile RAM device 70 and a massstorage device 72 that are all coupled to the bus 62. The mass storagedevice 72 may contain medical files of the patient that can be accessedby the user at the remote control station 16. For example, the massstorage device 72 may contain a picture of the patient. The user,particularly a health care provider, can recall the old picture and makea side by side comparison on the monitor 24 with a present video imageof the patient provided by the camera 38. The robot antennae 45 may becoupled to a wireless transceiver 74. By way of example, the transceiver74 may transmit and receive information in accordance with IEEE 802.11b.

The controller 54 may operate with a LINUX OS operating system. Thecontroller 54 may also operate MS WINDOWS along with video, camera andaudio drivers for communication with the remote control station 16.Video information may be transceived using MPEG CODEC compressiontechniques. The software may allow the user to send e-mail to thepatient and vice versa, or allow the patient to access the Internet. Ingeneral the high level controller 50 operates to control communicationbetween the robot 12 and the remote control station 16.

The remote control station 16 may include a computer that is similar tothe high level controller 50. The computer would have a processor,memory, I/O, software, firmware, etc. for generating, transmitting,receiving and processing information.

The high level controller 50 may be linked to the low level controller52 by serial ports 76 and 78. The low level controller 52 includes aprocessor 80 that is coupled to a RAM device 82 and non-volatile RAMdevice 84 by a bus 86. Each robot 12 contains a plurality of motors 88and motor encoders 90. The motors 88 can actuate the movement platformand move other parts of the robot such as the monitor and camera. Theencoders 90 provide feedback information regarding the output of themotors 88. The motors 88 can be coupled to the bus 86 by a digital toanalog converter 92 and a driver amplifier 94. The encoders 90 can becoupled to the bus 86 by a decoder 96. Each robot 12 also has a numberof proximity sensors 98 (see also FIG. 1). The position sensors 98 canbe coupled to the bus 86 by a signal conditioning circuit 100 and ananalog to digital converter 102.

The low level controller 52 runs software routines that mechanicallyactuate the robot 12. For example, the low level controller 52 providesinstructions to actuate the movement platform to move the robot 12. Thelow level controller 52 may receive movement instructions from the highlevel controller 50. The movement instructions may be received asmovement commands from the remote control station or another robot.Although two controllers are shown, it is to be understood that eachrobot 12 may have one controller, or more than two controllers,controlling the high and low level functions.

The various electrical devices of each robot 12 may be powered by abattery(ies) 104. The battery 104 may be recharged by a batteryrecharger station 106 (see also FIG. 1). The low level controller 52 mayinclude a battery control circuit 108 that senses the power level of thebattery 104. The low level controller 52 can sense when the power fallsbelow a threshold and then send a message to the high level controller50.

The system may be the same or similar to a robotic system provided bythe assignee InTouch-Health, Inc. of Santa Barbara, Calif. under thename RP-7. The system may also be the same or similar to the systemdisclosed in U.S. Pat. No. 6,925,357 issued Aug. 2, 2005, which ishereby incorporated by reference.

FIG. 4 shows a display user interface (“DUI”) 120 that can be displayedat the remote station 16. The DUI 120 may include a robot view field 122that displays a video image provided by the camera of the robot. The DUI120 may also include a station view field 124 that displays a videoimage provided by the camera of the remote station 16. The DUI 120 maybe part of an application program stored and operated by the computer 22of the remote station 16.

In operation, the robot 12 may be placed in a home or a facility whereone or more patients are to be monitored and/or assisted. The facilitymay be a hospital or a residential care facility. By way of example, therobot 12 may be placed in a home where a health care provider maymonitor and/or assist the patient. Likewise, a friend or family membermay communicate with the patient. The cameras and monitors at both therobot and remote control stations allow for teleconferencing between thepatient and the person at the remote station(s).

The robot 12 can be maneuvered through the home or a facility bymanipulating the input device 32 at a remote station 16. The robot 10may be controlled by a number of different users. To accommodate forthis the robot may have an arbitration system. The arbitration systemmay be integrated into the operating system of the robot 12. Forexample, the arbitration technique may be embedded into the operatingsystem of the high-level controller 50.

By way of example, the users may be divided into classes that includethe robot itself, a local user, a caregiver, a doctor, a family member,or a service provider. The robot 12 may override input commands thatconflict with robot operation. For example, if the robot runs into awall, the system may ignore all additional commands to continue in thedirection of the wall. A local user is a person who is physicallypresent with the robot. The robot could have an input device that allowslocal operation. For example, the robot may incorporate a voicerecognition system that receives and interprets audible commands.

A caregiver is someone who remotely monitors the patient. A doctor is amedical professional who can remotely control the robot and also accessmedical files contained in the robot memory. The family and serviceusers remotely access the robot. The service user may service the systemsuch as by upgrading software, or setting operational parameters.

The robot 12 may operate in one of two different modes; an exclusivemode, or a sharing mode. In the exclusive mode only one user has accesscontrol of the robot. The exclusive mode may have a priority assigned toeach type of user. By way of example, the priority may be in order oflocal, doctor, caregiver, family and then service user. In the sharingmode two or more users may share access with the robot. For example, acaregiver may have access to the robot, the caregiver may then enter thesharing mode to allow a doctor to also access the robot. Both thecaregiver and the doctor can conduct a simultaneous tele-conference withthe patient.

The arbitration scheme may have one of four mechanisms; notification,timeouts, queue and call back. The notification mechanism may informeither a present user or a requesting user that another user has, orwants, access to the robot. The timeout mechanism gives certain types ofusers a prescribed amount of time to finish access to the robot. Thequeue mechanism is an orderly waiting list for access to the robot. Thecall back mechanism informs a user that the robot can be accessed. Byway of example, a family user may receive an e-mail message that therobot is free for usage. Tables I and II, show how the mechanismsresolve access request from the various users.

TABLE I Access Medical Command Software/Debug Set User Control RecordOverride Access Priority Robot No No Yes (1) No No Local No No Yes (2)No No Caregiver Yes Yes Yes (3) No No Doctor No Yes No No No Family NoNo No No No Service Yes No Yes Yes Yes

TABLE II Requesting User Local Caregiver Doctor Family Service CurrentLocal Not Allowed Warn current user of Warn current user of Warn currentuser of Warn current user of User pending user pending user pending userpending user Notify requesting Notify requesting user Notify requestinguser Notify requesting user that system is in that system is in use thatsystem is in use user that system is in use Set timeout = 5 m Settimeout = 5 m use Set timeout Call back No timeout Call back CaregiverWarn current user Not Allowed Warn current user of Warn current user ofWarn current user of of pending user. pending user pending user pendinguser Notify requesting Notify requesting user Notify requesting userNotify requesting user that system is that system is in use that systemis in use user that system is in in use. Set timeout = 5 m Set timeout =5 m use Release control Queue or callback No timeout Callback DoctorWarn current user of Warn current user of Warn current user of Notifyrequesting user Warn current user of of pending user pending userpending user that system is in use pending user Notify requesting Notifyrequesting Notify requesting user No timeout Notify requesting user thatsystem is user that system is in that system is in use Queue or callbackuser that system is in in use use No timeout use Release control Settimeout = 5 m Callback No timeout Callback Family Warn current userNotify requesting Warn current user of Warn current user of Warn currentuser of of pending user user that system is pending user pending userpending user Notify requesting use Notify requesting user Notifyrequesting user Notify requesting user that system is No timeout thatsystem is in use that system is in use user that system is in in use Putin queue or Set timeout = 1 m Set timeout = 5 m use Release Controlcallback Queue or callback No timeout Callback Service Warn current userNotify requesting Warn current user of Warn current user of Not Allowedof pending user user that system is in request pending user Notifyrequesting use Notify requesting user Notify requesting user user thatsystem is No timeout that system is in use that system is in use in useCallback No timeout No timeout No timeout Callback Queue or callback

The information transmitted between the station 16 and the robot 12 maybe encrypted. Additionally, the user may have to enter a password toenter the system 10. A selected robot is then given an electronic key bythe station 16. The robot 12 validates the key and returns another keyto the station 16. The keys are used to encrypt information transmittedin the session.

The robot 12 and remote station 16 transmit commands through thebroadband network 18. The commands can be generated by the user in avariety of ways. For example, commands to move the robot may begenerated by moving the joystick 32 (see FIG. 1). The commands arepreferably assembled into packets in accordance with TCP/IP protocol.Table III provides a list of control commands that are generated at theremote station and transmitted to the robot through the network.

TABLE III Control Commands Command Example Description drive drive 10.00.0 5.0 The drive command directs the robot to move at the specifiedvelocity (in cm/sec) in the (x, y) plane, and turn its facing at thespecified rate (degrees/sec). goodbye goodbye The goodbye commandterminates a user session and relinquishes control of the robotgotoHomePosition gotoHomePosition 1 The gotoHomePosition command movesthe head to a fixed “home” position (pan and tilt), and restores zoom todefault value. The index value can be 0, 1, or 2. The exact pan/tiltvalues for each index are specified in robot configuration files. headhead vel pan 5.0 tilt The head command controls the head motion. 10.0 Itcan send commands in two modes, identified by keyword: either positional(“pos”) or velocity (“vol”). In velocity mode, the pan and tilt valuesare desired velocities of the head on the pan and tilt axes, indegree/sec. A single command can include just the pan section, or justthe tilt section, or both. keepalive keepalive The keepalive commandcauses no action, but keeps the communication (socket) link open so thata session can continue. In scripts, it can be used to introduce delaytime into the action. odometry odometry 5 The odometry command enablesthe flow of odometry messages from the robot. The argument is the numberof times odometry is to be reported each second. A value of 0 turnsodometry off. reboot reboot The reboot command causes the robot computerto reboot immediately. The ongoing session is immediately broken off.restoreHeadPosition restoreHeadPosition The restoreHeadPositionfunctions like the gotoHomePosition command, but it homes the head to aposition previously saved with gotoHomePosition. saveHeadPositionsaveHeadPosition The saveHeadPosition command causes the robot to savethe current head position (pan and tilt) in a scratch location intemporary storage so that this position can be restored. Subsequentcalls to “restoreHeadPosition” will restore this saved position. Eachcall to saveHeadPosition overwrites any previously saved position.setCameraFocus setCameraFocus 100.0 The setCameraFocus command controlsfocus for the camera on the robot side. The value sent is passed “raw”to the video application running on the robot, which interprets itaccording to its own specification. setCameraZoom setCameraZoom 100.0The setCameraZoom command controls zoom for the camera on the robotside. The value sent is passed “raw” to the video application running onthe robot, which interprets it according to its own specification.shutdown Shutdown The shutdown command shuts down the robot and powersdown its computer. stop stop The stop command directs the robot to stopmoving immediately. It is assumed this will be as sudden a stop as themechanism can safely accommodate. timing Timing 3245629 500 The timingmessage is used to estimate message latency. It holds the UCT value(seconds + milliseconds) of the time the message was sent, as recordedon the sending machine. To do a valid test, you must compare results ineach direction (i.e., sending from machine A to machine B, then frommachine B to machine A) in order to account for differences in theclocks between the two machines. The robot records data internally toestimate average and maximum latency over the course of a session, whichit prints to log files. userTask userTask “Jane Doe” The userTaskcommand notifies the robot of “Remote Visit” the current user and task.It typically is sent once at the start of the session, although it canbe sent during a session if the user and/or task change. The robot usesthis information for record-keeping.

Table IV provides a list of reporting commands that are generated by therobot and transmitted to the remote station through the network.

TABLE IV Reporting Commands Command Example Description abnormalExitabnormalExit This message informs the user that the robot software hascrashed or otherwise exited abnormally. Te robot software catches top-level exceptions and generates this message if any such exceptionsoccur. bodyType bodyType 3 The bodyType message informs the stationwhich type body (using the numbering of the mechanical team) the currentrobot has. This allows the robot to be drawn correctly in the stationuser interface, and allows for any other necessary body-specificadjustments. driveEnabled driveEnabled true This message is sent at thestart of a session to indicate whether the drive system is operational.emergencyShutdown emergencyShutdown This message informs the stationthat the robot software has detected a possible “runaway” condition (anfailure causing the robot to move out of control) and is shutting theentire system down to prevent hazardous motion. odometry odometry 10 20340 The odometry command reports the current (x, y) position (cm) andbody orientation (degrees) of the robot, in the original coordinatespace of the robot at the start of the session. sensorGroup group_dataSensors on the robot are arranged into groups, each group of a singletype (bumps, range sensors, charge meter, etc.) The sensorGroup messageis sent once per group at the start of each session. It contains thenumber, type, locations, and any other relevant data for the sensors inthat group. The station assumes nothing about the equipment carried onthe robot; everything it knows about the sensors comes from thesensorGroup messages. sensorState groupName state data The sensorStatecommand reports the current state values for a specified group ofsensor. The syntax and interpretation for the state data is specific toeach group. This message is sent once for each group at each sensorevaluation (normally several times per second). systemError systemErrorThis message informs the station user of a driveController failure inone of the robot's subsystems. The error_type argument indicates whichsubsystem failed, including driveController, sensorController, headHome.systemInfo systemInfo wireless 45 This message allows regular reportingof information that falls outside the sensor system such as wirelesssignal strength. text text “This is some The text string sends a textstring from the text” robot to the station, where the string isdisplayed to the user. This message is used mainly for debugging.version version 1.6 This message identifies the software versioncurrently running on the robot. It is sent once at the start of thesession to allow the station to do any necessary backward compatibilityadjustments.

The processor 54 of the robot high level controller 50 may operate aprogram that determines whether the robot 12 has received a robotcontrol command within a time interval. For example, if the robot 12does not receive a control command within 2 seconds then the processor54 provides instructions to the low level controller 50 to stop therobot 12. Although a software embodiment is described, it is to beunderstood that the control command monitoring feature could beimplemented with hardware, or a combination of hardware and software.The hardware may include a timer that is reset each time a controlcommand is received and generates, or terminates, a command or signal,to stop the robot.

The remote station computer 22 may monitor the receipt of video imagesprovided by the robot camera. The computer 22 may generate and transmita STOP command to the robot if the remote station does not receive ortransmit an updated video image within a time interval. The STOP commandcauses the robot to stop. By way of example, the computer 22 maygenerate a STOP command if the remote control station does not receive anew video image within 2 seconds. Although a software embodiment isdescribed, it is to be understood that the video image monitoringfeature could be implemented with hardware, or a combination of hardwareand software. The hardware may include a timer that is reset each time anew video image is received and generates, or terminates, a command orsignal, to generate the robot STOP command.

The robot may also have internal safety failure features. For example,the robot may monitor communication between the robot controller and therobot servo used to operate the platform motors. The robot monitor mayswitch a relay to terminate power to the platform motors if the monitordetects a lack of communication between the robot controller and themotor servo.

The remote station may also have a safety feature for the input device32. For example, if there is no input from the joystick for a certaintime interval (eg. 10 seconds) the computer 22 may not relay subsequentinput unless the user presses a button for another time interval (eg. 2seconds), which reactivates the input device.

The system may also scale one or more robot control commands based on anetwork parameter. By way of example, the remote control station mayscale the velocity component of the “drive” command before transmissionto the robot. FIG. 5 shows a process for scaling a robot controlcommand. In block 200 the station may determine a scale transferfunction based on a ping time. A ping time is the amount of time betweenwhen a test sample is sent from the remote station to the robot, to whenthe station receives the sample from the robot. In block 202 the stationmay determine a scale transfer function based on a video rate. The videorate is the rate at which the station receives frames of video from therobot camera.

The scale can be calculated in block 204. The scale y can be determinedin accordance with the following linear piece wise functions.y=Y ₁ for x≤X _(cutIn)y=Y ₂ for x>X _(cutOff)y=Y ₁ +s×(x−X _(cutoff)) for X _(cutIn) <x≤X _(cutOff)where y is the scale,S=Y ₁ −Y ₂)(X _(cutIn) −X _(cutOff))

-   -   x is the input variable, such as ping time or video rate; and,    -   the capitalized entities are constant values determined by the        application.

FIG. 6 is a graph that shows scale transfer functions based on ping timefor a common cut-in value of 150 msec (X_(cutIn)) and cut-off values of500, 750 and 1000 msec (X_(cutOff)). FIG. 7 is a graph that shows scaletransfer functions based on video rates for a common cut-in value of 0fps and cut-off values of 15, 20, 25 and 30 fps.

The scale can be determined utilizing both the ping time and the videorate. For example, the scale can be computed with the followingequation:Combined_scale=p×Ping_time_scale+(1.0−p)×Video_rate_scale

The parameter p may have a default value of 0.5 so that the ping timeand video rate have equal weight.

Referring again to FIG. 5, the calculated scale is filtered with a lowpass filter in block 206. The low pass filter 206 can be defined by thefollowing general equation:f _(i) =α×f _(in)+(1.0−α)×f _(i-1)

where

-   -   f_(i) is the current output    -   f₁₋₁ is the previous output    -   f_(in) is the current input, and    -   α is a constant that depends on the sampling period and the        filter's cut-off frequency.

The robot control command can be scaled in block 208. By way of example,the velocity command can be scaled with the calculated filtered scalevalue. Scaling the velocity command can control robot movement inresponse to changes in network latency. For example, the system canautomatically slow down the robot when there is an increase in thelatency of the network. This can assist in reducing overshoot orovercorrection by the user while driving the robot.

While certain exemplary embodiments have been described and shown in theaccompanying drawings, it is to be understood that such embodiments aremerely illustrative of and not restrictive on the broad invention, andthat this invention not be limited to the specific constructions andarrangements shown and described, since various other modifications mayoccur to those ordinarily skilled in the art.

What is claimed is:
 1. A remote controlled robot system, comprising: arobot that includes a camera and moves in response to a robot controlcommand; and, a remote control station that includes a monitor and iscoupled to said robot through a network, said remote control stationtransmits said robot control command that includes information to movesaid robot, wherein the robot control command includes a user-generatedvelocity command generated by the remote control station based on userinput received via a user input device of the remote control station andwherein the remote controlled robot system scales said robot controlcommand based on a monitored network parameter.
 2. The system of claim1, wherein said scaled robot control command is linearly proportional tosaid network parameter.
 3. The system of claim 1, wherein said networkparameter includes a ping time.
 4. The system of claim 3, wherein saidnetwork parameter includes a video rate.
 5. The system of claim 1,wherein said network parameter includes a video rate.
 6. The system ofclaim 1, wherein said scaled robot control command is filtered with alow pass filter.
 7. The system of claim 1, wherein said scaled robotcommand reduces a speed of said robot with an increase in a networklatency.
 8. The system of claim 1, wherein said robot includes amonitor, speaker and microphone and said remote control station includesa camera, speaker and microphone.
 9. A method for remotely controlling arobot that has a camera, the method comprising: displaying, on a monitorof the remote control station, an image captured by a camera of therobot; generating, by the remote control station, a robot controlcommand, wherein the robot control command includes a user-generatedvelocity command based on user input received via a user input device ofthe remote control station; monitoring at least one network parameter;scaling, by the remote control robot system, the robot control commandbased on the monitored network parameter; and moving the robot inaccordance with the scaled robot control command.
 10. The method ofclaim 9, wherein the scaled robot control command is linearlyproportional to the network parameter.
 11. The method of claim 9,wherein the network parameter includes a ping time.
 12. The method ofclaim 11, wherein the network parameter includes a video rate.
 13. Themethod of claim 9, wherein the network parameter includes a video rate.14. The method of claim 9, further comprising filtering the scaled robotcontrol command with a low pass filter.
 15. The method of claim 9,wherein the scaled robot command reduces a speed of the robot with anincrease in a network latency.